Provisioning non-commercial Microsoft NCE SKUs
In this release, we are introducing the capability to provision non-commercial Microsoft NCE SKUs. Partners and customers will be able to purchase non-commercial SKUs such as educational, government, and non-profit editions, provided they qualify for these purchases. Previously, partners and customers had to create manual versions of non-commercial SKUs, which is a time-consuming process. There was also the risk of partners offering discounts to ineligible customers.
In order to provision non-commercial SKUs, the edition code for Microsoft products has to be updated to include the customer segment. The updated edition code with the segment must be in the following format:
<product-id>:<sku-id>:<segment>, where <segment> is either "commercial," "education," or "nonprofit."
To update the edition code for non-commercial SKUs,
- Go to Manage > Marketplace > Products. Select a product from the Production Catalog, and click Edit Product.
- In the EDITIONS AND PRICING section, expand Editions, and then click a pricing edition to update.
- In the Edition Code field, enter the edition code in the above format. For example, if the Product ID is ABCDEF, SKU ID is 0001, and the segment is education, the Edition Code should be updated as ABCDEF:0001:education.
Company Admins must add these segments at the company level, which determines the behavior of purchase. This is also important to ascertain whether customers qualify to buy a product for the specified segment.
To set up segments at the company level and submit qualification requests:
- Go to Manage > Marketplace > Companies. Click on a company to open the Company Details page.
- Click on the Tenants tab. Click the ellipsis button, and click New Special Qualification Request.
- In the Special Qualification field, select a special qualification type.
- Select a segment and enter the URL of a related/supporting website, if any.
- Click Submit to Microsoft.
- Go back to the Company details page. On the Tenants tab, click the ellipsis button, and then click Sync Qualification Request. As the validation of qualification eligibility is an asynchronous process, this action is required to sync the status of the qualification request to determine whether the customer is indeed eligible for the particular qualification.
During the purchase (self-serve and assisted) of the products with special qualifications, the eligibility of the customer is validated using the Get a customer's qualification asynchronously API. If a customer is ineligible for the purchase, an error message is displayed, and they can submit a new special qualification request to see if they qualify.
Feature enablement
The feature is not enabled by default. Contact your AppDirect technical representative to request it.
Setting enablement
Setting enablement is required. Contact your AppDirect technical representative for more information.
Documentation
Documentation will be updated in the next release.
Was this page helpful?
Tell us more…
Help us improve our content. Responses are anonymous.
Thanks
We appreciate your feedback!